Support Dashboard
Executive Summary
Release Intelligence · GitHub Analysis
Key Finding
Bug volume has surged 148% from the February low — from 44 bugs in Feb 2–15 to 109 in Feb 28–Mar 13 — reversing the earlier declining trend. The March periods (P5 & P6) now contain 216 bugs combined, exceeding the 211 bugs in the first 4 periods together.
The initial Jan–Feb decline (68 → 52 → 44 → 47) has fully reversed. March saw major feature work including Override Pool architecture, Deductions & Accruals module, Multi-Milestone Overrides, and LMS Feature Flag, driving issue counts back above the January peak levels. Engineering velocity remained very high (311 + 372 merged PRs) while the bug queue expanded sharply.
44
Feb 2–15
Bugs at low
109
Feb 28–Mar 13
New peak
+148%
Bug surge
from low
Frontend releases per period overlaid on issue count
Total merged PRs (Backend + Frontend) — proxy for engineering change velocity
316
merged PRs
Staging features promoted to PRODUCTION simultaneously:
Frontend: 40 releases. Backend: CI/CD direct to prod. 68 bugs.
331
merged PRs
Jan 5–18 launch fallout and active backdating development:
Highest PR count of any early period (331). 52 bugs.
323
merged PRs
Position Backdating core module ships:
Bug count hit the all-time low of 44 this period.
320
merged PRs
Backdating custom fields persistence and stabilization:
47 bugs. Last period before the March surge.
311
merged PRs
Major feature development driving new issue peak:
109 bugs — highest ever. 148 BE + 163 FE merged PRs. Override Pool alone spanned 5+ architectural PRs.
372
merged PRs
Major new modules landing alongside highest PR velocity:
372 merged PRs — highest ever. 107 bugs. Highest engineering velocity alongside sustained high bug volume.
⚠ Bug Trend Has Reversed
Bugs per period: 68 → 52 → 44 → 47 → 109 → 107. The early 2026 decline fully reversed in March. The Feb 28–Mar 13 period set a new all-time bug peak of 109, and Mar 14–30 sustained it at 107. March alone has more bugs (216) than Jan+Feb combined (211).
📈 Velocity vs Quality Tradeoff
PR velocity peaked at 372 in P6 (Mar 14–30) while bugs remained above 100. The team is shipping faster than ever (Override Pool, D&A Module, Multi-Milestone Overrides) but the bug queue is not declining. New complexity is generating bugs faster than fixes resolve them.
🔧 Resolution Rate Declining
Resolution rate dropped from 98% (P1) to 53% (P6). The backlog is growing — nearly half of P6 issues remain unresolved. This creates compounding pressure as new periods add issues on top of unresolved ones from prior periods.
Overview
Section 1 — Severity
Stacked by severity across bi-weekly periods
Tracks highest-severity issues per period — key risk indicator
Section 2 — Engineering Throughput
% of tickets with Status = Done within each period
Count of non-Done tickets by status category
Section 3 — Direction of Travel
Actual bug count per bi-weekly period with trendline
Bug % change vs previous period
% of bugs that are Critical or High priority each period
Each functional area shown separately across all 6 periods
Section 4 — Critical Load Concentration
Top 10 clients — which clients carry the most critical load
Top 10 functional areas — which areas attract the highest-severity issues
Section 5 — Product Engineering Focus
Top 9 issue labels + Other as doughnut
Stacked bar — which areas were most affected each period
Section 6 — Customer Impact
Horizontal bar sorted by total issue count (excl. "All")
Stacked bar — which clients drove volume each period
Section 7 — Nature of Problems
Stacked count by issue type across all periods
Count of each type per period — spot shifts in the mix
100% stacked — share of bugs vs all other types each period
All-time breakdown across all filtered issues
Section 8 — Volume Context
Bi-weekly issue volume
Running total — shows overall pace of issue reporting
Section 9 — Operational Detail
Repository split across periods
Breadth of impact — distinct clients raising issues
Issue count by priority (row) and type (col) — darker = higher
Quality Initiative — Engineering Response
Response Summary
In response to the upward trend in reported issues during Feb 15 – Mar 14 (82 → 124 tickets, bugs 57% → 86%), the following measures were implemented — resulting in a sustained downward trend through Mar 29 – Apr 10 with a 77% drop in ticket volume and resolution rate climbing to 86%.
↓77%
Ticket volume
reduction
86%
Resolution
rate
Concentrated fix sprints across the top 5 problem areas identified from ticket patterns.
AI PR review workflow scans every pull request for regressions, type errors, and logic issues before human review.
All new features ship behind our home-built feature flag panel, available per server instance — enabling controlled rollout and instant kill-switch.
Migrated production servers to AWS Graviton for performance and replaced Sentry with NewRelic for deeper observability.
Extracted shared logic into centralized services, reducing code duplication and the surface area for inconsistency bugs.